In designing the best solution one must keep in mind the resources available and what the benefit would bring. The best solutions are often the most simple and eloquent. Therefore, since we have little ROI, cost and potential benefit metrics at our disposal and there does not appear to be funds to support another individual to guide PI’s through this process we should safely assume that, using a system, which would be automated, could result in unsatisfactory results. As automation is brought into place as a means for improvement to human processes which are already well defined, given this process is not well defined taking the shape of a developmental sharepoint space, with basic knowledge and flow charts would be best. Perhaps using google docs would also allow for simple, cost effective sharing of information without a need for expensive systems and processes.
The simpler the solution, starting with the first milestone in creating documentation and flowcharts of what already exists and adding to it where as second, going from what already exists, establishing trends and anticipating areas which would be ripe for automation and could benefit from systems. Once things are more established and better defined then systems and gauges can be established to determine if this system calls for Porsche level sophistication or the free and available google bicycle.
http://struts.apache.org/#Newbies
In designing the best solution one must keep in mind the resources available and what the benefit would bring. The best solutions are often the most simple and eloquent. Therefore, since we have little ROI, cost and potential benefit metrics at our disposal and there does not appear to be funds to support another individual to guide PI’s through this process we should safely assume that, using a system, which would be automated, could result in unsatisfactory results. As automation is brought into place as a means for improvement to human processes which are already well defined, given this process is not well defined taking the shape of a developmental sharepoint space, with basic knowledge and flow charts would be best. Perhaps using google docs would also allow for simple, cost effective sharing of information without a need for expensive systems and processes.
The simpler the solution, starting with the first milestone in creating documentation and flowcharts of what already exists and adding to it where as second, going from what already exists, establishing trends and anticipating areas which would be ripe for automation and could benefit from systems. Once things are more established and better defined then systems and gauges can be established to determine if this system calls for Porsche level sophistication or the free and available google bicycle.